Skip to content

Conversation

@MaggieKimani1
Copy link
Contributor

Fixes #1786

Copy link
Member

@darrelmiller darrelmiller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if you remove the code that removes the x-nullable this PR looks good.

Copy link
Member

@darrelmiller darrelmiller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. Although we should add a test case for when someone provides type as an array and also provides the nullable keyword. It should never happen but the current code would fail if it does.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 2, 2024

@MaggieKimani1 MaggieKimani1 merged commit f1c9297 into release/2.0.0 Oct 2, 2024
9 checks passed
@MaggieKimani1 MaggieKimani1 deleted the mk/handle-schemas-with-multiple-types branch October 2, 2024 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle upcast and downcast of JSON Schemas with multiple types

3 participants